| | [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #1796
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 2 - Low, e.g. a documentation error or undocumented side-effect |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Documentation |
|---|
| Summary: | Fl_Window::size_range() docs should indicate zero a special value for minh/minw |
|---|
| Version: | 1.1-current |
|---|
| Created By: | greg.ercolano |
|---|
| Assigned To: | mike |
|---|
| Fix Version: | 1.1-current (SVN: v6004) |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
No files
Trouble Report Comments:
| |
| #1 | greg.ercolano
22:44 Sep 26, 2007 |
| It would appear that if minh or minw are set to zero,
the value is ignored, falling back to the fltk/window manager defaults.
maxw/maxh document zero as a special value, but not minw/minh.
Current docs read:
minw and minh are the smallest the window can be.
Suggested modification:
minw and minh are the smallest the window can be. A value of zero for either will cause that value to be ignored, retaining the default behavior for that dimension. | |
| |
| #2 | StanS
06:40 Sep 27, 2007 |
| From a documentation standpoint, I'd suggest that there is an
ambiguity with respect to minw (res minh) == maxw (res maxh) == 0,
which should be clarified.
From a usability standpoint, I'd suggest that it be resolved
in such a way that size_range(W, 0) means "the minimum width shall be W,
the minimum height shall be 0 (i.e., no minimum)," similarly
for size_range(0, H). | |
| |
| #3 | mike
08:34 Nov 20, 2007 |
| Documentation issue; 0 (and values smaller than the minimum size supported by the window manager/system) are generally ignored or "clipped". | |
| |
| #4 | matt
02:03 Dec 18, 2007 |
| Fixed documentation, stating that minw and minh must be greater than 0. | |
[ Return to Bugs & Features ]
|
| |
